Question: What is the current version of Open Transport, and what are its key features?
Answer: Open Transport v1.1.1. This "rapid response" release is an update to Open Transport v1.1, to address the most pressing customer requests, in advance of the next feature release of Open Transport (currently planned as OT 1.5 - see Future Directions). Open Transport v1.1.1 includes the following updates and new features as compared to the earlier Open Transport 1.1 release:
• now also supports the Performa 5200, 5300, 6200, and 6300 systems;
• includes internal changes to minimize memory fragmentation resulting
from dynamic loading and unloading of TCP/IP;
• includes changes to the TCP/IP DNR for interoperability with sites using
the load-balancing name daemon;
• includes changes for support of the upcoming Open Transport/PPP release;
• includes all bug fixes available to date.
Question: How is Open Transport v1.1.1 available?
Answer: Open Transport v1.1.1 is built as a stand-alone installer, and is distributed online from a variety of Apple, and Internet sites.
Question: Does System 7.5.3 or System Update 2.0 include Open Transport 1.1.1?
Answer: No. MacOS system software ships with Open Transport 1.1. Open Transport 1.1.1 was not yet available at the time these products went to manufacturing. Future releases of MacOS system software are planned to include the most current release of Open Transport available at the time. However, incremental updates to OT may be provided independantly (such as with OT 1.1.1) to provide responsive customer support.
Question: Does the Open Transport single-user software package contain Open Transport 1.1.1?
Answer: No. The retail software package ships with Open Transport 1.1. Open Transport 1.1.1 was not yet available at the time this product went to manufacturing. Current plans call for the Open Transport software package to be updated with each feature-based release of Open Transport; however, incremental updates to OT may also be provided independantly (such as with OT 1.1.1) as needed to provide responsive customer support.
Question: Are there changes in the system requirements for Open Transport 1.1.1?
Answer: There are no changes from the previous release, Open Transport 1.1, in the memory, processor, or OS requirements (see Open Transport and MacOS System 7.5.3). Installation of Open Transport 1.1.1 requires that a previous version of Open Transport already be installed and (on applicable systems) selected as the active network system via the NSS.
Question: What of the earlier Open Transport 1.1 release?
Answer: Open Transport v1.1 included the following updates and new features as compared to the earlier 1.0.x releases:
• added support for 68030 and 68040 MacOS systems,
• added support for PowerPC MacOS systems with NuBus,
• added support for NuBus, SCSI, and CommSlot network interface adapters,
• offered tuning to optimize performance of high speed datalinks,
• offered tuning to support multiple client, multithreaded server
applications,
• added support for multinode and multihomed operation of AppleTalk
protocols,
• added support for raw packet access and promiscuous mode, to enable the
development of Open Transport-ready network analyzers and other network
management utilities,
• recognized a significantly expanded selection of MacTCP dial-up network
extensions (mdevs),
• allowed reconnection of a dial-up TCP/IP session without reloading
networking and without system restart,
• provided display of the datalink Media Access Control address for
Ethernet and token ring networks,
• provided user notification in the event duplicate AppleTalk or TCP/IP
addresses are established,
• automatically converted user's existing AppleTalk and MacTCP setting to
Open Transport configuration files during installation (only if Open
Transport preferences do not already exist),
• included improved compatibility with Apple Remote Access 2.0.1,
• included improved compatibility with a wider range of DHCP servers,
• provided a basis for future support for PPP-based AppleTalk and TCP/IP
remote networking,
• provided a basis for future support for modem and ISDN communications
devices,
• included support for MacOS system software System 7.5.3,
• included support for the creation of a "universal system folder",
• included support for the Network Software Selector utility to provide
easy transition from classic to Open Transport networking on MacOS
systems supporting both,
• offered improved Balloon Help text for System 7 users, and,
• included all bug fixes available to date.
Question: How is Open Transport v1.1 available?
Answer: Open Transport v1.1 is available through a broad range of distribution channels:
• as a no-charge upgrade to customers with existing MacTCP volume license
software maintenance agreements;
• as a no-charge upgrade to customers with existing system software volume
license software maintenance agreements;
• as a component of MacOS system software release System 7.5.3;
• as a component of MacOS system software update System 7.5 System Update
2.0;
• as a retail software product in single-user software package;
• through an OEM redistribution licensing program from Apple Software
Licensing,
• bundled with Apple and third party applications software that are Open
Transport-ready; and,
• from select Apple-licensed publishers and Internet Service Providers.
Question: How do volume license software maintenance customers receive Open Transport?
Answer: A master copy of the Open Transport software and documentation is automatically be mailed to the contact of record for customers with active MacTCP or MacOS System Software maintenance contracts.
Question: How could a customer receive a copy of System 7.5.3?
Answer: System 7.5.3 will be pre-installed on MacOS systems beginning in first half calendar 1996. System 7.5.3 will also become available as a shrink-wrap retail product in first half calendar 1996.
Question: How could a customer receive a copy System 7.5 System Update 2.0?
Answer: System 7.5 System Update 2.0 is available through a variety of channels, including:
• On the Internet, from locations including www.info.apple.com,
www.support.apple.com, ftp.info.apple.com, and ftp.support.apple.com;
• On electronic information services such as eWorld, America Online, and
CompuServe;
• Through Apple User Groups; and,
• From the Apple Order Center, in floppy or CD update kits. The update is
available at no charge plus $13 shipping and handling. Call U.S. +1
(800) 293-6617, ext. 984 to order.
Question: What is the part number and pricing for the Open Transport single-user software package?
Answer: In the U.S. order number M4252Z/A; the estimated retail price is $39.
Question: Since Open Transport is included with System Update 2.0 and System 7.5.3, why might a customer want to purchase the Open Transport single-user software package?
Answer: The Open Transport single-user software package is designed for customers running System 7.1.x who are not ready to upgrade to System 7.5.3, yet want to take advantage of Open Transport features. It might also be of interest to customers running System 7.5.3 who want a printed copy of the user documentation.
Question: Is Open Transport localized for non-English speaking countries?
Answer: As a part of MacOS System 7.5.3, Open Transport 1.1 is being localized around the world. Please contact the Apple Assistance Center in your area for details. Availability of localized versions of OT 1.1.1 will vary on a country by country basis.
Question: How is Open Transport available to software developers, publishers, and/or Internet Service Providers (ISPs) for redistribution and bundling?
Answer: Apple offers two different redistribution licensing agreements for Open Transport, designed to meet the needs of publishers, software developers, and ISPs.
The first agreement is designed for Internet service providers, network and communications reference work authors and publishers, and others interested in bundling Open Transport software as an added customer benefit to their product or service offering. This license is based on a sliding-scale per-unit license fee, and requires annual reporting of licenses issued. Interested parties should send electronic mail to SW.LICENSE@applelink.apple.com.
The second agreement is designed for software developers with products that adopt the new Open Transport APIs who wish to ship Open Transport as a part of an integrated product installation process. This agreement is based on an addendum to the MacOS SDK, and allows qualified developers to ship the Open Transport run-time environment to end-users as a part of their product.
To qualify, developers must execute the Open Transport License Addendum through Apple Software Licensing, and meet the following requirements:
• have developed an Open Transport-ready or Open Transport-enhanced
software product (including applications developed for Apple's
NetSprockets game architecture),
• be current subscribers to the MacOS SDK,
• provide Apple advance notice of their intent to ship their Open
Transport product(s), distribute the required Open Transport components
only in conjunction with their product(s), and,
• annually report the total number of licenses issued.
Other terms and conditions apply, however, no additional fees (beyond the MacOS SDK subscription) are required for this license. Interested parties can send electronic mail to SW.LICENSE@applelink.apple.com.
Question: Will localized versions of Open Transport software be available for developer and ISP licensing?
Answer: Initially the Open Transport redistribution licensing program will only have the U.S. English version of the software available. Licensing of localized versions of Open Transport will depend upon demand and availability.
Question: What of the earlier Open Transport v1.0.x releases?
Answer: Open Transport v1.0.x releases were all designed for use only on the Apple PCI Macintosh systems:
• Open Transport version 1.0, for the Power Macintosh 9500, was focused on
offering compatibility with existing networking client applications and
on upgrading the feature set and performance of TCP/IP. It shipped only
as an integral part of system software with the 9500.
• Version 1.0.1 was a maintenance update, designed to correct a potential
problem with data truncation in large file transfers. Open Transport
v1.0.1 was distributed electronically, as an update to be applied to an
existing installation of Open Transport v1.0.
• Version 1.0.6 added support for the Power Macintosh 7200, 7500, and 8500
systems and addressed bugs discovered since the 1.0 release. Open
Transport v1.0.6 shipped as a component of System Software 7.5.2 version
2 on the Power Macintosh 7200, 7500, 8500, and 9500 models.
• Version 1.0.7 included changes to improve performance and compatibility
of Open Transport/TCP with third party SLIP and PPP software and with
certain Internet Service Providers (ISPs). Open Transport v1.0.7 was
distributed electronically, as an update to be applied to an existing
installation of Open Transport v1.0.6.
• Version 1.0.8 was also a maintenance release, and included better
compatibility with Qualcomm Eudora, Claris Emailer and Emailer Lite, CE
Software QuickMail, and Netscape Communications client software, as well
as improvements in BootP and DHCP interoperability. Open Transport
v1.0.8 was distributed via a variety of information services - such as
AppleLink and eWorld, and a number of Internet sites - as a full
installation of Open Transport software.
Question: Why was Open Transport made available on PCI Power Macintosh systems first?
Answer: Starting with the introduction of the Power Mac 9500, Apple moved to adopt industry standards for both network driver software - Open Transport DLPI - and network hardware - PCI. This strengthened the business case for new and existing third party developers who could, as a result, include MacOS on PowerPC in their plans for cross-platform network connectivity products. The Power Macintosh 9500 was the first system to incorporate both of these standards, and has since been followed by additional systems and configurations.
In particular, Apple made the business decision to move to standards for networking on the hardware and software fronts in tandem, that is, PCI and DLPI. This created a dependency that required customers deploy Open Transport with their PCI MacOS systems. It also minimized the work by third parties needed to create drivers for new PCI networking cards. As a result customers have found a broad selection of third party PCI networking options for MacOS.
